RaceTracker Pro — Journey Test Report

Race Setup

3 passed

creates a new race from scratch and verifies the overview

A race director fills in all the details needed to create a brand-new race — the race name, date, start time, how many checkpoints there are, and the range of runner bib numbers. Once saved, the race overview page should correctly display the race name, list every checkpoint, and show the right number of registered runners.

22.4s passed

01-A Home — Welcome Back screen with 3 module cards

01-B Home — Welcome Back screen with 3 module cards

02-A Race Maintenance → Create New Race — setup wizard opens

02-B Race Maintenance → Create New Race — setup wizard opens

03-A Step 1 of 4 — Template: choose Start from Scratch

03-B Step 1 of 4 — Template: choose Start from Scratch

04-A Step 2 of 4 — Race Details: enter name, date, start time and checkpoints

04-B Step 2 of 4 — Race Details: enter name, date, start time and checkpoints

05-A Step 3 of 4 — Runner Setup: add bib number range 101–115

05-B Step 3 of 4 — Runner Setup: add bib number range 101–115

06-A Step 4 of 4 — Waves: confirm wave and save race

06-B Step 4 of 4 — Waves: confirm wave and save race

07-A Race overview — name, 3 checkpoints and 15 runners correct

005 route → /race-maintenance/overview?raceId=1

07-B Race overview — name, 3 checkpoints and 15 runners correct

08-A Home — new race listed under module cards

08-B Home — new race listed under module cards

step indicator advances correctly through setup wizard

The race creation wizard has four steps: Template, Race Details, Runner Setup, and Waves. This test checks that the progress indicator at the top updates as you advance through each step, so the race director always knows where they are in the setup process.

17.8s passed

01-A Step 1 of 4 — Template: setup wizard opens

01-B Step 1 of 4 — Template: setup wizard opens

02-A Step 2 of 4 — Race Details: step indicator shows step 2

02-B Step 2 of 4 — Race Details: step indicator shows step 2

03-A Step 3 of 4 — Runner Setup: step indicator advances to step 3

03-B Step 3 of 4 — Runner Setup: step indicator advances to step 3

back button on step 2 returns to race details with data preserved

If a race director fills in the race name and other details on Step 2 of 4 (Race Details), moves on to Step 3 of 4 (Runner Setup), then clicks Back, all their work should still be there — the race name and other fields must not be wiped out. Nobody should have to retype information just because they went back a step.

18.5s passed

01-A Step 1 of 4 — Template: choose Start from Scratch

01-B Step 1 of 4 — Template: choose Start from Scratch

02-A Step 2 of 4 — Race Details: fill in race name and details

02-B Step 2 of 4 — Race Details: fill in race name and details

03-A Step 3 of 4 — Runner Setup: navigate forward then press Back

03-B Step 3 of 4 — Runner Setup: navigate forward then press Back

04-A Step 2 of 4 — Race Details: data preserved after Back

04-B Step 2 of 4 — Race Details: data preserved after Back

Checkpoint Operations

6 passed

navigates to checkpoint and sees runner grid

A checkpoint volunteer opens the app, taps "Checkpoint Operations", selects their race, and arrives at the correct checkpoint screen. This test confirms that the grid of runner bib numbers — the list of every runner they need to watch for — is visible and fully loaded.

7.2s passed

01-A Home — tap Checkpoint Operations module card

003 route → /race-maintenance/overview?raceId=1

01-B Home — tap Checkpoint Operations module card

02-A Select Race modal — choose race from list

02-B Select Race modal — choose race from list

03-A Checkpoint view — runner grid loaded with bib numbers 200–210

03-B Checkpoint view — runner grid loaded with bib numbers 200–210

marks off a single runner via the runner grid

A checkpoint volunteer clicks on a single runner's bib number tile in the grid to record that the runner passed through. The tile should change colour or appearance to make it obvious that runner has been marked as "through".

21.9s passed

01-B Checkpoint view — runner grid visible

02-A Runner grid — tap first runner tile (200s range)

02-B Runner grid — tap first runner tile (200s range)

marks off multiple runners via Quick Entry

Instead of finding runners in the grid, a volunteer can just type a bib number and press Enter to record it quickly. This test enters two bib numbers one after the other using the quick-entry shortcut and confirms both runners are marked off.

9.3s passed

01-A Checkpoint view — Quick Entry bar visible

01-B Checkpoint view — Quick Entry bar visible

02-A Quick Entry — type first bib number and press Enter

02-B Quick Entry — type first bib number and press Enter

03-A Quick Entry — type second bib number and press Enter

03-B Quick Entry — type second bib number and press Enter

04-A Runner grid — both runners marked off

04-B Runner grid — both runners marked off

switches to Callout Sheet tab

The Callout Sheet tab shows the list of runners who have not yet been recorded at this checkpoint. Volunteers read these numbers out over the radio to base station. This test checks the tab loads correctly and the list is visible.

6.8s passed

01-A Checkpoint view — Mark Off tab active

01-B Checkpoint view — Mark Off tab active

03-A Callout Sheet — unrecorded runners listed

03-B Callout Sheet — unrecorded runners listed

switches to Overview tab and shows runner counts

The Overview tab shows a summary — how many runners have been through, how many are still expected, and other totals. This test confirms those summary numbers appear correctly when the tab is selected.

6.8s passed

01-A Checkpoint view — navigate to checkpoint

01-B Checkpoint view — navigate to checkpoint

03-A Overview — runner count summary visible

03-B Overview — runner count summary visible

can export checkpoint results

At the end of a checkpoint shift, a volunteer may need to export their recorded data to share with base station or keep as a backup. This test checks that the export option can be opened from the checkpoint screen.

21.6s passed

03-A Export dialog — checkpoint results export options shown

03-B Export dialog — checkpoint results export options shown

Base Station

0 passed 6 failed

navigates to base station and sees data entry form

A base station operator opens the app, taps "Base Station Operations", selects their race, and lands on the data entry screen. This test confirms the form for entering finish times and runner bib numbers is ready to use.

5.6s skipped

enters a common time and runner batch, then verifies in overview

The most common base station task: the operator types in a finish time (for example 10:45:00) then lists all the runner bib numbers who crossed the finish line at that time. After submitting, those runners should appear in the overview with their recorded finish time.

5.7s skipped

records a DNF via the withdrawal dialog

When a runner drops out of the race and does not finish (DNF), the base station operator needs to record this. This test opens the withdrawal dialog, enters a runner's bib number and a reason such as "Injured ankle", confirms the entry, and checks that the runner now shows a DNF status in the overview.

5.6s skipped

opens the Checkpoint Matrix tab

The Checkpoint Matrix gives a bird's-eye view of where all runners are across every checkpoint in the race. This test checks that switching to the Checkpoint Matrix tab loads and displays checkpoint information correctly.

5.6s skipped

switches to Reports tab and renders a report

The Reports tab lets the operator generate a printed summary of race results. This test switches to the tab and checks that the report content — runner totals, times, and status counts — is visible.

5.6s skipped

exports base station data

The base station operator may need to export all their recorded data for backup or to share with the race director. This test checks that the import/export tool can be opened from the base station screen.

5.7s skipped

Race Management

7 passed

race management page lists created races

The Race Management page is the race director's central hub where all races are listed. This test confirms that a race created earlier in the test suite appears on that page.

20.5s passed

01-A Race Management — page lists all created races

01-B Race Management — page lists all created races

004 route → /race-maintenance/overview?raceId=1

clicking a race opens its overview

When the race director clicks on a race in the management list, they should be taken to that race's overview page where they can see all the details. This test confirms that navigation works correctly.

20.9s passed

01-A Race Management — page with race listed

01-B Race Management — page with race listed

02-A Race card — click race name to open overview

02-B Race card — click race name to open overview

03-A Race overview — name and details visible

03-B Race overview — name and details visible

creates a second race from the management page

A race director creates a second race directly from the management screen, going through the full two-step setup wizard (race details, then runner ranges) and landing on the new race's overview page.

21.0s passed

01-A Race Management — tap Create New Race button

01-B Race Management — tap Create New Race button

02-A Step 1 of 4 — Template: choose Start from Scratch

02-B Step 1 of 4 — Template: choose Start from Scratch

03-A Step 2 of 4 — Race Details: enter name, date, start time

03-B Step 2 of 4 — Race Details: enter name, date, start time

04-A Step 3 of 4 — Runner Setup: add bib range 500–503

04-B Step 3 of 4 — Runner Setup: add bib range 500–503

05-A Step 4 of 4 — Waves: confirm and save

05-B Step 4 of 4 — Waves: confirm and save

06-A Race overview — second race created successfully

06-B Race overview — second race created successfully

race overview shows correct runner and checkpoint counts

After creating a race with runner bib numbers 400 to 405 (6 runners) and 2 checkpoints, the race overview page should display "6" as the runner count and "2" as the checkpoint count — no more, no less.

20.8s passed

01-A Race overview — runner count 6 and checkpoint count 2 shown

01-B Race overview — runner count 6 and checkpoint count 2 shown

navigates from race overview to a checkpoint

From the race overview, a race director can jump straight to any checkpoint's live mark-off screen. This test clicks the Checkpoint 1 link and confirms the checkpoint mark-off screen opens.

5.0s passed

navigates from race overview to base station

From the race overview, a race director can jump straight to the base station. This test clicks the Base Station button on the overview page and confirms the base station operations screen opens.

4.9s passed

home page landing shows the race management module card

The Race Maintenance module card should always be visible on the home screen so race directors can always find it easily. This test simply confirms the card is present.

15.7s passed

01-A Home — Race Maintenance module card visible

01-B Home — Race Maintenance module card visible

Navigation Protection

4 passed

shows protection modal when leaving active checkpoint operation

While a checkpoint volunteer is actively recording runners, the app should warn them if they try to navigate away — for example by tapping the back button or going to a different module. This prevents accidentally losing all their recorded data. This test triggers that navigation and confirms the warning appears.

6.2s passed

01-A Checkpoint view — navigate directly to /checkpoint/1

02-A Attempt navigation away — go to home /

02-B Attempt navigation away — go to home /

03-A Protection modal — operation warning or graceful fallback

03-B Protection modal — operation warning or graceful fallback

allows navigation after confirming exit from active operation

If a volunteer sees the "you're about to leave an active session" warning and confirms they want to leave anyway, the app should let them go and return them to the home screen. This test confirms that confirming the exit actually works.

6.3s passed

01-A Checkpoint view — navigate to /checkpoint/1

02-A Confirm exit — trigger exit and accept confirmation

02-B Confirm exit — trigger exit and accept confirmation

03-A Navigation complete — landed on non-checkpoint route

03-B Navigation complete — landed on non-checkpoint route

home page module cards are all accessible when no operation is active

When the app is idle on the home screen and no operation is in progress, all three module cards — Checkpoint Operations, Base Station, and Race Maintenance — should be enabled and ready to tap. This test confirms none of them are accidentally disabled.

5.5s passed

01-A Home page — all module cards visible and enabled

01-B Home page — all module cards visible and enabled

unknown routes redirect to home

If someone types a web address that doesn't exist in the app (perhaps a typo or an old bookmark), they should be automatically sent to the home page rather than seeing a blank or broken screen.

5.7s passed

01-A Unknown route — redirects to home page

004 page load → /this/route/does/not/exist

01-B Unknown route — redirects to home page

Settings

3 passed

opens and closes the Settings modal

Tapping the settings cog in the top-right corner should open the settings panel. Pressing the Escape key (or tapping close) should dismiss it cleanly. This test confirms both actions work.

16.3s passed

01-A Home — tap Settings cog button (aria-label Settings)

01-B Home — tap Settings cog button (aria-label Settings)

02-A Settings modal — panel open with customisation options

02-B Settings modal — panel open with customisation options

03-A Settings modal — closed after pressing X button

03-B Settings modal — closed after pressing X button

toggles dark mode on and off

The dark mode toggle in settings switches the app between a light colour scheme and a dark one. This test turns dark mode on, confirms the dark theme is applied, then turns it back off and confirms the light theme is restored.

16.5s passed

02-A Settings modal — locate Dark Mode toggle switch

02-B Settings modal — locate Dark Mode toggle switch

03-A Dark mode ON — html element gains "dark" class

03-B Dark mode ON — html element gains "dark" class

04-A Dark mode OFF — "dark" class removed from html element

04-B Dark mode OFF — "dark" class removed from html element

settings persist after closing and reopening the modal

Changes made in settings should be saved and remembered. If dark mode is turned on and the settings panel is closed then reopened, dark mode should still be on — the preference should not reset.

16.9s passed

02-A Settings modal — enable dark mode and save

02-B Settings modal — enable dark mode and save

04-A Settings modal — dark mode toggle persists as checked

04-B Settings modal — dark mode toggle persists as checked

Import Export

0 passed 3 failed

export modal opens from base station header

The base station screen has an import/export button in the header. This test confirms that tapping it opens the data portability dialog where the operator can choose what to export.

0.1s skipped

downloads a race configuration JSON file

This test triggers the export function and confirms that a JSON file is actually downloaded to the device. The file should contain the race configuration — name, checkpoints, runner numbers — that can be used to restore the race on another device.

20.0s skipped

01-A Race Management — page with created race listed

01-B Race Management — page with created race listed

02-A Race card — open export / download option

imports a race configuration and restores data

After wiping all data from the app, this test uploads a previously exported race file and confirms the race is fully restored — the race name, checkpoints, and runner numbers all come back exactly as they were before the data was cleared.

0.1s skipped